Update 7.0 to use Ubuntu 22.04 queues for Perf runs #90767
Conversation
* Because crossgen need LTTng and 22.04 is not compatible. * Windows using same queue.
|
Tagging subscribers to this area: @hoyosjs Issue DetailsThis updates the servicing branches to use the new Ubuntu 22.04 queues. Customer ImpactNone, as this does not change product code. Regression?No. TestingCurrently running on main branches successfully RiskLow. This is not a product change, and as such I expect the risk to be zero.
|
jeffschwMSFT
left a comment
jeffschwMSFT
left a comment
There was a problem hiding this comment.
approve. we should consider this tell mode. adding @carlossanlop to assist on when we can merge.
carlossanlop
added
Servicing-approved
|
Tagging subscribers to this area: @dotnet/runtime-infrastructure Issue DetailsThis updates the servicing branches to use the new Ubuntu 22.04 queues. Customer ImpactNone, as this does not change product code. Regression?No. TestingCurrently running on main branches successfully RiskLow. This is not a product change, and as such I expect the risk to be zero.
|
|
The release/7.0 branch is currently closed. Is it ok if we wait until the branches open again next month so that your same change which was merged into release/7.0-staging is flowed into the release/7.0 branch? (Which means closing this PR). |
|
If the branch is closed, does that mean that there will be no additional check-ins until the branch opens up? If that is the case then this should be fine, as long as this goes in before other things. |
|
You can merge all the changes you want into the |
lewing
added
Servicing-approved
|
Merging now. @DrewScoggins in the future, if you need to submit servicing PRs to the runtime repo, please target the |
ghost
locked as resolved and limited conversation to collaborators
5 participants
This updates the servicing branches to use the new Ubuntu 22.04 queues.
Customer Impact
None, as this does not change product code.
Regression?
No.
Testing
Currently running on main branches successfully
Risk
Low. This is not a product change, and as such I expect the risk to be zero.